home *** CD-ROM | disk | FTP | other *** search
- Path: news.ultranet.com!usenet
- From: "Albert P. Belle Isle" <belleisl@cerberus-sys.com>
- Newsgroups: alt.winsock,alt.winsock.trumpet,comp.dcom.modems
- Subject: Re: Comm Overrun Errors - A Possible Solution
- Date: 2 Feb 1996 14:50:12 GMT
- Organization: Cerberus Systems, Inc.
- Message-ID: <4et8b4$1k9@caesar.ultra.net>
- References: <4emn1a$5ba@trojan.neta.com> <4esm85$qd2@fountain.mindlink.net>
- NNTP-Posting-Host: apb-p5-90.cerberus-sys.com
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 1.22 (Windows; I; 16bit)
-
- dennis_goos@mindlink.bc.ca (dennis goos) wrote:
- >
- >Following a tip from someone else,I disabled 32-bit access (in control panel
- >-virtual memory] and ALL the comm overruns that had been occurring after I
- >replaced Win3.11 with WFWG disappeared.
- >I wish I knew why !
-
-
- Dennis:
-
- One cause of tardy system response to com port Interrupt ReQuests
- (which is what causes overruns) is poorly written 32-bit disk drivers
- which are not completely WD1003-compatible (needed for Windows' caching
- software to work properly).
-
- This locks-out IRQs of lower priority than the disk IRQ (like com port
- interrupts) for an inordinately long time, when it arbitrarily decides to
- dump-to-disk a large write-behind cache it's been saving for the middle
- of your most critical large file download.
-
- While awaiting longer term fixes by upgrading disk-drivers (or BIOS, or
- disk), you can get some relief by turning off write-behind caching (for
- VCACHE in WFWG and SMARTDRV in Win), but it sounds like you need to
- upgrade your disk setup.
-
- You might want to take a look at the OVERRUNS section of the below-listed
- FAQ for a little more detail, or at John Navas' excellent Modem FAQ for a
- lot (see my FAQ's LINKS section).
-
- Windows for Workgroups is a vastly more powerful OS than Windows, and was
- used as the test-bed for many of the features of the "Chicago" project
- (which became Win4/DOS7 - marketed as "Windows 95").
-
- It's a true pre-emptive multi-tasking system for DOS-window applications,
- for instance. (It still has crummy old "cooperative" multi-tasking for
- Windows apps, however.) It also has a much higher speed (Ring-0) "virtual
- device driver" (VxD) for its com ports, for which its "comm.drv" is just
- a (Ring-3) front-end to provide compatibility with older Windows
- applications. (Which is why "improved," 3rd-party comm.drv replacements
- for regular Windows shouldn't be used with WFW.)
-
- Its 32-bit file- and disk-access features (also using high-speed VxDs)
- are a pretty potent performance enhancement to surrender because of an
- out-of-date disk driver or BIOS. Next to the amount of RAM (which
- substitutes for disk), disk speed is the biggest factor in system speed
- (far more than CPU speed for most applications.)
-
- Even if you need a new disk, today's prices are pretty low, especially if
- you go for speed without the largest possible size.
-
- Regards,
-
- Al
-
- --
- ==================================================================
- Albert P. Belle Isle
- Cerberus Systems, Inc.
-
- Al's Winsock Tuning FAQ -
- http://www.cerberus-sys.com/~belleisl/mtu_mss_rwin.html
- ==================================================================
-
-
-